Skip to content

Conversation

jvaclavik
Copy link
Contributor

@jvaclavik jvaclavik commented Oct 4, 2025

Idea

Don't you see your trezor? and Troubleshooting tips buttons (see screenshot below) have similar intention (something is not working, so how to fix the issue?). But visual representation and behaviour of these two buttons were totally different. I unified these two actions to similar experience in this PR.

image

Related Issue

Resolve

Screenshots:

Welcome screen

Screenshot 2025-10-04 at 14 41 18 Screenshot 2025-10-04 at 14 40 06 Screenshot 2025-10-04 at 14 39 58 Screenshot 2025-10-04 at 14 39 09 Screenshot 2025-10-04 at 14 38 46 Screenshot 2025-10-04 at 14 37 57

Welcome screen (non-subtle button)

It's for cases where Troubleshooting button is now expanded by default (there is no other primary action)

Screenshot 2025-10-04 at 14 40 29 Screenshot 2025-10-04 at 14 38 26

Troubleshooting Modal

image image image

🔍🖥️ Suite web test results: View in Currents

🔍🖥️ Suite desktop test results: View in Currents

🔍🖥️ Suite native android test results: View in Currents

@jvaclavik jvaclavik requested a review from a team as a code owner October 4, 2025 12:37
@jvaclavik jvaclavik marked this pull request as draft October 4, 2025 12:37
@jvaclavik jvaclavik self-assigned this Oct 4, 2025
@jvaclavik jvaclavik force-pushed the update-troubleshooting-tips branch from 0b7b77b to b33119b Compare October 4, 2025 13:01
@trezor-bot
Copy link
Contributor

trezor-bot bot commented Oct 4, 2025

✅ Previously successful run of [Test] PR Suite Desktop e2e tests workflow has been found.
⏭️ Skipping tests for this run.
💡 If you are unsure about your latest changes, please rerun the workflow manually. (Use the Re-run all jobs option)

@trezor-bot
Copy link
Contributor

trezor-bot bot commented Oct 4, 2025

✅ Previously successful run of [Test] PR Suite Web e2e tests workflow has been found.
⏭️ Skipping tests for this run.
💡 If you are unsure about your latest changes, please rerun the workflow manually. (Use the Re-run all jobs option)

@jvaclavik jvaclavik force-pushed the update-troubleshooting-tips branch 2 times, most recently from 07af187 to 222034a Compare October 4, 2025 14:14
expect(findByTestId('@connect-device-prompt')).not.toBeNull();
expect(findByTestId(/TR_DEVICE_IN_BOOTLOADER/)).not.toBeNull();
expect(findByTestId('TR_DEVICE_CONNECTED_BOOTLOADER')).not.toBeNull();
fireEvent.click(findByTestId('@onboarding/troubleshooting-tips/button'));
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMHO it's really bad practice to check hidden content, it was pretty hard to debug 🤷‍♂️

Now we click first before we check.

@jvaclavik jvaclavik force-pushed the update-troubleshooting-tips branch from c7072c1 to 330c22c Compare October 6, 2025 08:43
@jvaclavik jvaclavik force-pushed the update-troubleshooting-tips branch from 330c22c to 58915d7 Compare October 7, 2025 17:29
@jvaclavik jvaclavik marked this pull request as ready for review October 7, 2025 17:30
@jvaclavik jvaclavik merged commit b70f2f6 into develop Oct 7, 2025
29 checks passed
@github-project-automation github-project-automation bot moved this to 🤝 Needs QA in Suite Desktop Oct 7, 2025
@jvaclavik jvaclavik deleted the update-troubleshooting-tips branch October 7, 2025 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 🤝 Needs QA

Development

Successfully merging this pull request may close these issues.

2 participants